Trigger unexpectedly uninstalled

Hello,

I'm facing a strange behavior with triggers in DOORS 9.3.

I've one trigger installed at project level working fine and another installed at module level for all the modules in the project that is making me crazy.

This trigger (at module level) is installed as shown below:

t = trigger(sTriggerName,module->sModuleName->formal->attribute->sAttributeName, post, modify, 10, sTriggerDXLCode)

The problem is that the trigger is getting uninstalled automatically without any interaction from my side. I detected this issue because the trigger was not working and printing the information about the triggers installed I got "none".

I've tried to reinstall it again and it is saying that has been installed properly but after few minutes it disappear again.

1) does somebody know what is happening there?

2) is it a problem if somedoby in working on shareable mode while installing the trigger?

 

Thanks a lot in advance.


dacapri - Thu Feb 19 04:16:42 EST 2015

Re: Trigger unexpectedly uninstalled
llandale - Wed Feb 25 13:54:21 EST 2015

I am guessing you are trying to install this trigger in a specific list of modules in the project.

I am guessing it is actually getting deployed in the Project level, instead of the module level.

  • module->sModuleName               should deploy in that module, so long as it is open for edit.  This may also deploy in the Project
  • module->sModuleName->formal The "informal" is a way to select modules, so I'm guessing it deploys in the Project
  • module->.. attribute   Will be sufficient to deploy in the current module.

-Louie

I suggest you make this a project level trigger, it will get the module name and determine if it should do any work or not.

Re: Trigger unexpectedly uninstalled
dacapri - Mon Mar 02 11:44:08 EST 2015

llandale - Wed Feb 25 13:54:21 EST 2015

I am guessing you are trying to install this trigger in a specific list of modules in the project.

I am guessing it is actually getting deployed in the Project level, instead of the module level.

  • module->sModuleName               should deploy in that module, so long as it is open for edit.  This may also deploy in the Project
  • module->sModuleName->formal The "informal" is a way to select modules, so I'm guessing it deploys in the Project
  • module->.. attribute   Will be sufficient to deploy in the current module.

-Louie

I suggest you make this a project level trigger, it will get the module name and determine if it should do any work or not.

Hello Louie,

thanks for your reply.

I get in contact with IBM and they said that I'm using an old version of DOORS and that would be better to update it :s

As I said, the trigger is currently working fine (because I've reinstalled it) but the problem is that from time to time it is getting uninstalled automatically.

You suggestion to change it at project level and to make some check there is fine but also my solution should work. It's working now, why it should not work anymore in 1 week? :/

 

Many thanks.

Best Regards,

Daniele